| Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management 12c Release 3 (12.1.0.3) Part Number E24215-05 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management 12c Release 3 (12.1.0.3) Part Number E24215-05 |
|
|
PDF · Mobi · ePub |
Oracle Data Integrator (ODI) provides a fully unified solution for building, deploying, and managing complex data warehouses or as part of data-centric architectures in an SOA or business intelligence environment. In addition, it combines all the elements of data integration - data movement, data synchronization, data quality, data management, and data services - to ensure that information is timely, accurate, and consistent across complex systems.
An ODI domain contains the ODI components that can be managed using Enterprise Manager. An ODI domain contains:
One or several Oracle Data Integrator Console applications. An Oracle Data Integrator Console application is used to browse Master and Work repositories.
One or several Run-Time Agents attached to the Master Repositories. These agents must be declared in the Master Repositories to appear in the domain. These agents may be Standalone Agents or Java EE Agents.
The Repositories and Agent pages display both application metrics and information about the Master and Work Repositories.
This chapter describes the set of typical tasks you need to perform when managing Oracle Data Integrator:
Before you start managing ODI with Enterprise Manager, you must:
Deploy the Oracle Management Agent
Oracle Management Agents must be installed on the database hosting the ODI repositories. Optionally, an Oracle Management Agent can also be installed on a machine hosting an ODI Agent.
See Installing the Oracle Management Agent in the Oracle Enterprise Manager Cloud Control Basic Installation Guide
Discover ODI Target
ODI target discovery is part of the Fusion Middleware discovery. Two target types are available: ODI Standalone Agent and ODI Java EE Agent. See Chapter 2, "Discovering Middleware Targets" for additional information.
Along with ODI specific targets it also discovers domain and admin server.
Discover the Database
Each Oracle Database Server needs to be discovered because more than one database could be hosting the ODI repositories.
All the operations are available out-of-box in Enterprise Manager.
To access Oracle Data Integrator (ODI), perform the following steps:
From the Targets menu on Enterprise Manager, select Middleware.
In the Middleware Features menu, select ODI Home.
The ODI Home tab appears.
The regions on this page include:
Master Repositories Health
Work Repositories Health
Agents Health
Data Servers Health
Search
The following summarizes the tasks to perform when managing Oracle Data Integrator components.
Starting, Stopping, and Restarting Oracle Data Integrator Agents
Search Sessions and Load Plan Executions.
Navigate to the LPE/Sessions tab under ODI Home Page.
To start, stop, and restart Oracle Data Integrator agents, use the Enterprise Manager Fusion Middleware Control Console.
You can manage the agent status and monitor its activities.
The steps for this process are:
Click the target link corresponding to your Java EE Agent either in the target navigation pane or in the ODI Master Repository Home Page. The Java EE Application Page for this agent appears.
From the Agent Page menu, select Monitoring then select Performance Summary.
The Performance Summary page opens. You can view and customize the displayed metrics and charts. How?
You can view log messages of Java EE agents in Enterprise Manager Cloud Control.
The steps for this process are:
Navigate to the ODI Agent Home page.
From the ODI Agent menu, select Logs then select View Log Messages.
You can filter the displayed log messages, for example by date range and message type and search for a search term in the message.
To configure the log configuration settings, select Logs then select Log Configuration from the ODI Agent menu.
Oracle Data Integrator (ODI) provides a fully unified solution for building, deploying, and managing complex data warehouses or as part of data-centric architectures in a SOA or business intelligence environment.
In addition, ODI combines all the elements of data integration - data movement, data synchronization, data quality, data management, and data services - to ensure that information is timely, accurate, and consistent across complex systems.
Click the links for information regarding each of the tabs on this page.
ODI provides statistics summarizing the general health of the following components:
Master Repositories
ODI Agents
Work Repositories
Data Servers
This section reports on the:
Number of master repositories that are either up or down. Click the number for a list of the repositories.
Master Repositories with Incidents. Click the number to find out which repositories have incidents.
To resolve issues reported in this section:
If the ODI repositories are down, act based on the statuses by either bringing up the repositories which are down or troubleshoot why they are down and resolve the issues.
If there are any repositories which are undiscovered, discover the repositories in Cloud Control.
If there are any repositories with alerts, identify the root cause for those alerts and resolve the issues.
This section reports on the:
Number of Agents that are either up or down. Click the number for a list of the Agents.
Number of Agents that are not discovered as targets in Enterprise Manager. Click the number for a list of the Agents that have not been discovered.
Number of Agents with Incidents. Click the number to find out which repositories have incidents.
To resolve issues reported in this section:
If the Agents are down, act based on the statuses by either bringing up the Agents which are down or troubleshoot why they are down and resolve the issues.
If there are any Agents which are undiscovered, discover the Agents in Cloud Control.
If there are any Agents with alerts, identify the root cause for those alerts and resolve the issues.
This section reports on the:
Number of work repositories that are either up or down. Click the number for a list of the repositories.
Number of work repositories that have not been discovered. Click the number of a list of the work repositories that have not been discovered.
Work Repositories with Incidents. Click the number to find out which repositories have incidents.
To resolve issues reported in this section:
If the ODI repositories are down, act based on the statuses by either bringing up the repositories which are down or troubleshoot why they are down and resolve the issues.
If there are any repositories which are undiscovered, discover the repositories in Cloud Control.
If there are any repositories with alerts, identify the root cause for those alerts and resolve the issues.
This section reports on the:
Number of data servers that are either up or down. Click the number for a list of the servers.
Number of data servers that have not been discovered. Click the number of a list of the data servers that have not been discovered.
Data Servers with Incidents. Click the number to find out which data servers have incidents.
To resolve issues reported in these sections:
If the data servers are down, act based on the statuses by either bringing up the data servers which are down or troubleshoot why they are down and resolve the issues.
If there are any data servers which are undiscovered, discover the data servers in Cloud Control.
If there are any data servers with alerts, identify the root cause for those alerts and resolve the issues.
Load Plan Executions/Sessions Quick Links
Click the links for details for each of the following:
| Link Name | Description |
|---|---|
| Sessions With Errors | Number of sessions in error for this agent. |
| Sessions With Error Records | Number of sessions with error records for this agent. |
| LPEs With Errors | Number of load plan executions in error for this agent. |
| LPEs With Error Records | Number of load plan executions with error records for this agent. |
This page has a table containing the following columns:
The Agents section displays the Agents declared in the Master Repository.
| Element | Description |
|---|---|
| Name | Displays the name of the Agent. Select an Agent to display the corresponding Agent Home page. |
| Discovery Status | A blue tick indicates that the ODI Agent is discovered as a custom target in Enterprise Manager.
A clock indicates that the ODI Agent is not discovered as a custom target in Enterprise Manager. |
| View Performance | Click the eye glass icon to view the performance data of the Agent. The metrics include:
|
| Active Sessions | Displays the number of active sessions. |
| Master Repository | A check mark acknowledges that this is a Master Repository. |
| Version | Displays the version and date of the Agent. |
| Response Time (ms) | Repository database response time in milliseconds. |
| User Defined Alerts | Displays the number of Critical and Warning alerts. Click the number to view the alerts in the Incident Manager page. |
Use this region to search for agents for all Java EE and Standalone agents.
The latest specified search criteria are always retained. Specify a new criteria and click Search to see the updated results. Or, click Reset to reset the search form (you must still click Search to see the updated results). Note that the search criteria are reset each time you log out or navigate away from all the tabbed pages of the Oracle Data Integrator Console application.
| Element | Description |
|---|---|
| Master Repository | Select the Master Repository. |
| Execution Agent | Select an Agent from the drop-down list. You can also select All to list all the Agents. |
| Agent Status | Select the status of the agent: Up, Down, All. |
| Discovery Status | Select the status of the agent: Discovered, Not Discovered, All. |
The Repositories tab displays the following regions:
Note: Credentials have to be selected for this region to display.
| Element | Description |
|---|---|
| Name | Displays the name of the Work Repository. |
| Status | Displays the status of the Work Repository database.
|
| Host | Displays the name of the host on which the repository resides. |
| Port | Displays the port of the host on which the repository resides. |
| SID | Displays the system identifier of the repository. |
| Version | Displays the Repository version. |
| Response Time (ms) | Repository database response time in milliseconds. |
| External ID | Displays the ODI-specific unique identifier for the repository. |
| Incidents | Displays the number of incidents associated with this repository: Critical or Warning. |
| Schema Name | Displays the name of the schema associated with this repository. |
| LPE/Sessions Tablespace | Total Rows and Segment Size in GB. |
| Purge | Click the icon to purge the ODI logs. A separate browser window appears where you provide the required information, for example, purge type. |
By looking at the database details, you have a clear picture of how your database is performing. For example, if the Database Table Space is reaching near full, the Database Administrator can look at extending the table space.In addition, by taking a look at the database performance chart, Throughput and Wait bottlenecks sections, the Database Administrator can recommend fine tuning the database.
Wait Bottlenecks
This section provides the following statistics: Average Instance (CPU%), Active Sessions Waiting I/O, and Active Sessions Waiting Others.
Throughput
This section provides the following statistics: Number of Transactions per second, Physical Writes per transaction, Physical Reads per transaction, and User Commits per transaction.
Performance
This section provides usage information for CPU, I/O Wait, and Others for the active sessions.
Note: Credential and repository have to be selected for this region to display.
This section provides the growth rate for the tablespace by providing Space Used and Space Allocated statistics. Based on the information, you can decide whether to archive or purge the database data, or extend the tablespace.
Use this region to search for repositories for all master and work repositories.
The latest specified search criteria are always retained. Specify a new criteria and click Search to see the updated results. Or, click Reset to reset the search form (you must still click Search to see the updated results). Note that the search criteria are reset each time you log out or navigate away from all the tabbed pages of the Oracle Data Integrator Console application.
| Element | Description |
|---|---|
| Repository Type | Select the Repository type: Master Repository, Work Repository, All. |
| Repository Name | Enter the name or a part of the Repository name. |
| Repository Status | Select the status of the Repository: Up, Down, All. |
| Discovery Status | Select the status of the repository: Discovered, Not Discovered, All. |
The Load Plan Executions/Sessions displays the execution details of the Load Plan Executions and Sessions executed by the Agent.
Expand a session and review the Steps and Tasks information. For example if an ODI Interface was executed, you can review each task that this interface executed, view the generated code, and drill down to the database execution details.
Note:
Oracle Database Diagnostics and Tuning Packs are required to use the SQL Drill Down feature.| Element | Description |
|---|---|
| Name | Displays the name of the Load Plan Execution or Session. |
| Execution ID | Load Plan Execution or Session identifier. Every time a Load Plan is executed, a new Load Plan Execution with a unique identifier is created. |
| Status | Displays the status of the Load Plan Execution run or Session executed.
|
| Started On | Start date and time of the Load Plan Execution/Session run. |
| Updated On | Displays the last updated date of the Load Plan Execution/Session. |
| Execution Time | Displays how long it took the Load Plan Execution/Session to run. |
| Message | Displays the error message of the Load Plan Execution/Session run, if any. |
| Error Records | Displays the number of error records. |
| Execution Type | Displays the type LoadPlan or Sessions, for example, Scenario. |
| Work Repo Name | Displays the name of the Work Repository into which this Load Plan/Session run execution information is stored. |
| Agent Name | Displays the name of the agent on which the Load Plan Execution/Session ran. |
| ODI User | Displays the name of the ODI user who started the execution. |
Use this region to search for sessions and load plan executions for all master and work repositories.
The latest specified search criteria are always retained. Specify a new criteria and click Search to see the updated results. Or, click Reset to reset the search form (you must still click Search to see the updated results). Note that the search criteria are reset each time you log out or navigate away from all the tabbed pages of the Oracle Data Integrator Cloud Control application.
| Element | Description |
|---|---|
| Master Repository | Select the Master Repository containing the session information. |
| Work Repository | Select the Work Repository containing the session information. |
| Execution Agent | Select the Agent used to execute the session. |
| Context | Select the session's execution context |
| Execution Type | Select Sessions, Load Plan Executions, or All. |
| Begin Date | Use the calendar icon to select a date at which to start the search for sessions. Only session started after this date will be returned |
| End Date | Use the calendar icon to select a date at which to end the search for load plan executions and sessions. Only load plan executions and sessions ended before this date will be returned. |
| User Name | Name of the ODI user who started the execution. |
| Status | Select All or narrow the search to display specific statuses: Error, Running, Done, Warning, or Waiting. For example, you can select to view only Running and Warning statuses. |
| Message | Error message of the Load Plan Execution/Session run. |
| Keywords | Type keywords to narrow the search. When using multiple keywords, use a comma to separate each keyword, do not include spaces. For example use: lpe1,lpe2. |
| Execution Name | Type the name of the load plan execution. |
| Error Records | Select All or narrow the search to display load plan executions and sessions With Error Records or Without Error Records. |
| Execution ID | Specific Load Plan Execution or Session identifier. |
The Agents Home page enables you to monitor the Oracle Data Integrator run-time Agents. Both Standalone agents and Java EE Agents are ODI job executors. The difference between the two agents is that the Standalone Agents are non Java EE based and are managed through Oracle Process Manager and Notification Server (OPMN) or Common Administration Model (CAM) from Enterprise Manager. These run on the Jetty web server. Java EE Agents are Java EE based, that is, they are deployed on Oracle WebLogic Servers or IBM WebSphere. (IBM WebSphere is supported for ODI release 11.1.1.7 only).
Note: OPMN will be used to manage ODI standalone agents until ODI release 11.1.1.7. CAM will be used to manage ODI Standalone agents from ODI release 12c and later.
The Agent Home page is arranged in the following order:
The General Info region displays general information about this Agent.
| Element | Description |
|---|---|
| Status | Displays the status of the Agent.
|
| Response Time (ms) | Displays the repository database response time in milliseconds. |
| Agent Version | Displays the version of the Agent. |
| Host and Port | Displays the host (network name or IP address) of the machine where the Agent has been launched on and the port on which the Agent is listening. |
| Master Repository | Click to access the Database Performance page for the Master Repository. |
| Incidents | An event or a set of closely correlated events that represent an observed issue requiring resolution through (manual or automated) immediate action or root-cause problem resolution. |
| More Information | Click to browse for more information in the Oracle Data Integrator Console. |
The Target Incidents region displays notifications raised by the Agents attached to this Repository.
| Element | Description |
|---|---|
| Severity | Seriousness of the incident.
|
| ID | Incident ID. |
| Summary | Summary description of the incident. |
| Category | Classification of an incident, for example, Error. |
The Load Balancing Agents region displays (if using ODI Load Balancing) the status and session metrics for the Agents declared as child Agents of the current Agent.
| Element | Description |
|---|---|
| Name | Displays the name of the agent. This is the name you specified when you created the Agent in Oracle Data Integrator. Select an Agent to display the corresponding Agent Home page. |
| Status | Displays the status of the Agent.
|
| Discovered | A blue tick indicates that the ODI Agent is discovered as a custom target in Enterprise Manager. Click the Agent name to access the ODI Console's Agent Detail Page.
A clock indicates that the ODI Agent is not discovered as a custom target in Enterprise Manager. Click the Agent name to access the Enterprise Manager Agent Target Page. |
| Originating LPEs/Sessions | Displays the status of the LPEs and Sessions.
|
| Avg Master Repo Response Time (ms) | Displays the master repository database response time in milliseconds. |
| Sessions | Maximum and Active number of sessions allowed on this Agent. |
| Threads | Maximum and Active number of threads allowed on this Agent. |
The Load region displays the number of connections supported by the Agent over a period of time.
| Elements | Description |
|---|---|
| Maximum number of allowed sessions | Maximum number of sessions allowed on this Agent. |
| Maximum number of allowed threads | Maximum number of threads allowed on this Agent. |
| Count of active sessions | Number of active sessions on this Agent. |
| Count of active threads | Number of active threads on this Agent. |
LPEs/Sessions Execution Incidents
The Load Plan Executions/Sessions Execution Incidents region displays notifications raised by the Agents attached to this Repository.
| Element | Description |
|---|---|
| Severity | Seriousness of the incident.
|
| ID | Incident ID. |
| Summary | Summary description of the incident. |
| Category | Classification of an incident, for example, Error. |
Oracle Data Integrator Console cannot be configured from Enterprise Manager Cloud Control. To make configuration changes you must use the Fusion Middleware Control Console. For information of how to configure Oracle Data Integrator, see Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
However, you can configure Oracle Data Integrator Console from Cloud Control to define the linking between Cloud Control and Oracle Data Integrator Console.
By default, the fields on this page are populated with the Oracle Data Integrator Console host, the Oracle Data Integrator Console managed server port, and the default context root. If your Oracle Data Integrator Console must be accessed with a different configuration, you can change the configuration on this page.
The steps for this process are:
Navigate to the Agent home page.
From the Agent Page menu, select ODI Console Administration then select Basic Configuration.
To modify the current configuration, enter new values in the following fields and click Apply.
Host: The name of the server where your application is deployed
Port: The HTTP listener port number
Context Root: The Web application's context root
Protocol: The protocol for the connection
Click Revert to revert to the previous settings.
Use the ODI Console Application Configuration page to configure the connection to the Oracle Data Integrator Console Application.This page displays the current configuration for accessing the Oracle Data Integrator Console application. These values are automatically set when the application is discovered by Enterprise Manager and are used to access Oracle Data Integrator Console from Enterprise Manager, for example when clicking Browse.You can modify these values to access Oracle Data Integrator Console in a different way, for example to connect to Oracle Data Integrator Console by using a load balancer.
To modify this configuration, enter new values in the fields and click Apply. Click Revert to revert to the previous settings.
| Element | Description |
|---|---|
| Host | Displays the name of the server where your application is deployed. If using SSO, enter the Oracle HTTP Server (OHS). |
| Port | Displays the HTTP listener port number. If using SSO, enter the port of the machine where Oracle HTTP Server 10g or 11g Webgate is installed. |
| Context Root | Displays the Web application's context root. |
| Protocol | Displays the protocol of the connection |
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
